fTPM: add enum to ta flags #97
Conversation
If we compile this TA into OPTEE-OS we need to define a flag that this TA can be discovered on the optee bus. Signed-off-by: Maxim Uvarov <[email protected]>
|
Ping to the maintainers. This should be an easy take. |
|
The Samples are untested and unmaintained and therefore are about to be removed from this repo. |
|
OK - where will they go to? This is critical for us. |
|
This change represents the reality that this repo is not a full TPM implementation. It has always been necessary to provide both a custom platform, (usually) custom crypto libraries, plus an outer interface for a particular implementation to create a "complete" TPM. Hence, it's best to keep those platforms and outer layers in their own repositories. https://github.com/microsoft/MSRSec is one such repo, though I don't know the intention of those maintainers, if any. The sample code here and at MSRSec are available to be forked/copied under the license agreement(s) of the appropriate repo (or the license agreement in the header of individual files, as the case may be). Our recommendation is for users who want to use them to create their own fork of MSRSec, or separate repositories for their custom TPM platforms, and include the core library from here as a submodule (like MSRsec does). The next release comes with CMake project files and can be incorporated into either larger CMake build systems, or other custom build systems. The last commit containing the existing Samples code here will be tagged and continue to be available for reference. |
3 participants
If we compile this TA into OPTEE-OS we need to define a flag that this TA can be discovered on the optee bus.
move microsoft/MSRSec#34 here.